feat: per-request OAuth2 auth override#6
Merged
marinofranz merged 3 commits intomainfrom Oct 31, 2025
Merged
Conversation
3 tasks
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR implements per-request authentication support, enabling OAuth2 bearer token authentication alongside the existing API key authentication. This is accomplished through a new
withAuth()method that allows reusing a single client instance with different credentials per request.Related Issue
Closes #5
Type of Change
Changes Made
Testing
pnpm test)Code Quality
pnpm lintand fixed any issuespnpm formatto format my codepnpm typecheckand there are no type errorsDocumentation
Additional Context
The proposed API design in #5 was not ideal after researching further and chose the
withAuth()pattern over alternative approaches (request-level parameters, middleware, etc.) because it avoids modifying method signatures across all resourcesChecklist
mainbranch